V305: FIX LEGACY CHARACTERS VISIBLE IN EVERY ACCOUNT
===================================================
The native BG2 Import screen reads every .CHR directly inside Documents/...
/characters/. It does not know which account owns those files.

V304 deliberately refused to delete old unassigned root CHR/BIO files. It
therefore refused to mount the new dra01/kro01 copies while those files were
present, leaving the old files visible to the unmodified game instead.

V305 adds an EXPLICIT manual isolation tool, not an automatic backup or recovery.

1) CLOSE EVERY BaldurII.exe and InfinityLoader.exe session. Log out normally.
2) Run ISOLATE_OLD_SHARED_CHARACTERS.bat from this ZIP.
3) Select the BG2 Documents folder that contains Baldur.lua (NOT the game EXE).
4) Carefully examine the loose CHR/BIO filenames listed in the preview.
5) Type ISOLATE if you agree. Otherwise exit without changing anything.
6) The utility MOVES ONLY flat characters/*.CHR and characters/*.BIO into
   _DRAKHYSYS_UNASSIGNED_ROOT_ISOLATION/group_####/ OUTSIDE characters/.
   It never touches characters/Drakhysys/, characters/Kronas/, account logins,
   or any nested account folder.
7) Run SETUP_IN_GAME_ACCOUNTS.bat with the desired BG2 profile if not already
   installed, then launch ordinary BaldurII.exe and log in.
8) Run CHECK_ACCOUNT_CHARACTER_ACCESS.bat. Native root should now have ONLY
   the logged account's temporary draXX/kroXX copies (or be empty if the
   account has no valid CHR). Import should no longer show old loose characters.

The isolated files are NOT automatically re-imported, reused, or restored.
They are not deleted. You can inspect the isolated group manually later.
BG2 engine built-in sample characters may still appear. No external router can
hide these without modifying the engine/UI Import listing.

If the tool refuses because the account is still marked active after a crash,
first make sure BG2 is closed; use RELEASE_STUCK_ACCOUNT_LOGIN.bat and repeat.
Do not discard old files until you personally verify what they contain.

V305 retains V304 account routing and numbered copies; it does not modify
multiplayer arbitration UI or change the character's in-game displayed name.
